Upstream v5.66.0 #4455
Closed
Upstream v5.66.0 #4455
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Does the PR have any schema changes?Found 5 breaking changes: Resources
Functions
Types
New resources:
New functions:
Maintainer note: consult the runbook for dealing with any breaking changes. |
|
Closing in favor of #4458 as the upgrade tests have flagged an upstream regression. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #4435
Upstream is upgraded to v5.66.0.
Notable upstream additions:
New resources:
datazone/environment.Environment
New functions:
glue/getRegistry.getRegistry
organizations/getOrganizationalUnitDescendantOrganizationalUnits.getOrganizationalUnitDescendantOrganizationalUnits
quicksight/getAnalysis.getAnalysis
quicksight/getQuicksightAnalysis.getQuicksightAnalysis
Unfortunately the aws_quicksight_analysis datasource cannot yet be fully supported in the provider because excessively large type hierarchies in Quicksight cause issues for Pulumi SDKs. This is the same problem that makes "definition" fields unavailable for Quicksight resources. A solution is being explored in #4449 but in the meantime the "definition" field is not available yet in Pulumi for the given datasource.